Subject: counters for non-configured connections

From: [email-masked]
Date: Mon, 31 Oct 94 14:22:39 -0500

A DLSw entity can be configured to originate transport connections to partner
DLSw entities.  The same DLSw entity can accept transport connections from
partner DLSw entities for which the DLSw entity is not configured to originate
transport connections.

The DLSw MIB requires a DLSw entity to maintain traffic (e.g., packet/octet) 
counter statistics for the DLSw traffic sent and received over transport 
connections regardless of whether or not the DLSw entity was configured to 
originate the transport connection.  The way in which a DLSw entity is expected
to manage the statistics counters for a particular transport connection depends
upon whether or not the DLSw entity was configured to originate the transport 
connection.  Closing a transport connection to a DLSw partner to which a DLSw
entity was configured to originate connections does not affect the traffic 
counter statistics for that connection.  However, closing a transport connection
to a DLSw partner to which a DLSw entity was not configured to originate 
connections clears the traffic counter statistics for that connection.

Therefore SNMP manager call accounting applications should not use the transport
traffic counter statistics that a DLSw entity maintains for any DLSw partners
to which the DLSw entity was not configured to originate connections because
the traffic counts can not be reliably obtained.  The traffic counter statistics
for these transport connections should be obtained from the DLSw partners that 
were configured to originate the connections.

Alan Sciacca